Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0b821d8c7b31bd1f8a68fa5e37106dc901066e2bca3fd12df11aa86f05c69e7e

Tx prefix hash: 3cd9a9c345f720e960a3de5aab435100a6615eb8b549628a8570430fc7fbce85
Tx public key: bf63a0d317f7dcd37577dd1e71174899260b17dbefc7153bbb3e5a50d8e43101
Timestamp: 1635288247 Timestamp [UCT]: 2021-10-26 22:44:07 Age [y:d:h:m:s]: 03:104:09:28:07
Block: 361145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 852801 RingCT/type: yes/0
Extra: 01bf63a0d317f7dcd37577dd1e71174899260b17dbefc7153bbb3e5a50d8e4310102110000000137cb3088000000000000000000

1 output(s) for total of 39.028072568000 dcy

stealth address amount amount idx
00: dea927dc6807a2fb5be37623d5d263afe78ef433aa66f453714e51f7e1af1fd0 39.028072568000 734854 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 361155, "vin": [ { "gen": { "height": 361145 } } ], "vout": [ { "amount": 39028072568, "target": { "key": "dea927dc6807a2fb5be37623d5d263afe78ef433aa66f453714e51f7e1af1fd0" } } ], "extra": [ 1, 191, 99, 160, 211, 23, 247, 220, 211, 117, 119, 221, 30, 113, 23, 72, 153, 38, 11, 23, 219, 239, 199, 21, 59, 187, 62, 90, 80, 216, 228, 49, 1, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8