Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b87f4ee31b186cf742fb7eb647aeb60093f7d5518407f4545eab1c38784d8a99

Tx prefix hash: 574d45b0a5efaaef1232114e15ef7c2c6f52f5a8843c8c18dcedfd946ea1ccbf
Tx public key: 08cd44b9b9a600cf1092bbf583e86eadb0701c577ca23c6b9776587349b0f1b6
Timestamp: 1729316104 Timestamp [UCT]: 2024-10-19 05:35:04 Age [y:d:h:m:s]: 00:200:13:37:06
Block: 1134785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143147 RingCT/type: yes/0
Extra: 0108cd44b9b9a600cf1092bbf583e86eadb0701c577ca23c6b9776587349b0f1b60211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1faad87dc8f8f739efc097223717a4c376e6594645e367eb5c56bc2d6eab889 0.600000000000 1618112 of 15

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": 1134795, "vin": [ { "gen": { "height": 1134785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1faad87dc8f8f739efc097223717a4c376e6594645e367eb5c56bc2d6eab889" } } ], "extra": [ 1, 8, 205, 68, 185, 185, 166, 0, 207, 16, 146, 187, 245, 131, 232, 110, 173, 176, 112, 28, 87, 124, 162, 60, 107, 151, 118, 88, 115, 73, 176, 241, 182, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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