Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7c8107de6952d8e9644f9f3ebc9c712b94cf9f35f7dd4ef1c5b38af7587441c

Tx prefix hash: 3548f1bf5a0075bfb3922cfc7e26b9829376caa80270a08a9d66e9570210674b
Tx public key: 45a521e1e534abd73e9141bd75fc1155ed7fdafd75158b38fb5340468cf334c3
Timestamp: 1724219214 Timestamp [UCT]: 2024-08-21 05:46:54 Age [y:d:h:m:s]: 00:247:13:02:45
Block: 1092544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176794 RingCT/type: yes/0
Extra: 0145a521e1e534abd73e9141bd75fc1155ed7fdafd75158b38fb5340468cf334c302110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b13b9a061e53f8f38a674afdc1418e927c815101e8c74bd0f63790e58b23c80 0.600000000000 1567311 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": 1092554, "vin": [ { "gen": { "height": 1092544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b13b9a061e53f8f38a674afdc1418e927c815101e8c74bd0f63790e58b23c80" } } ], "extra": [ 1, 69, 165, 33, 225, 229, 52, 171, 215, 62, 145, 65, 189, 117, 252, 17, 85, 237, 127, 218, 253, 117, 21, 139, 56, 251, 83, 64, 70, 140, 243, 52, 195, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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