Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef00767c5c20d0f6ece59c3353076c1bcf1a450a8eeba1acb73a3d6f57631e9c

Tx prefix hash: 871b87c90d21839374570ee4fbf88eac2bff8bd9f3c51ceb8b58007375c19b62
Tx public key: cd213e8f6a76175ace3e9ef8cd14f10f6f67220969e8593c9029b6b920a7a9df
Timestamp: 1635113363 Timestamp [UCT]: 2021-10-24 22:09:23 Age [y:d:h:m:s]: 03:062:22:14:32
Block: 359765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 823339 RingCT/type: yes/0
Extra: 01cd213e8f6a76175ace3e9ef8cd14f10f6f67220969e8593c9029b6b920a7a9df0211000000064a0f5013000000000000000000

1 output(s) for total of 39.441154486000 dcy

stealth address amount amount idx
00: 4914b2fd00126e516a09e6e74ecf8eddd0f8d498784f532deb4fb7b5c7e4c468 39.441154486000 732484 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": 359775, "vin": [ { "gen": { "height": 359765 } } ], "vout": [ { "amount": 39441154486, "target": { "key": "4914b2fd00126e516a09e6e74ecf8eddd0f8d498784f532deb4fb7b5c7e4c468" } } ], "extra": [ 1, 205, 33, 62, 143, 106, 118, 23, 90, 206, 62, 158, 248, 205, 20, 241, 15, 111, 103, 34, 9, 105, 232, 89, 60, 144, 41, 182, 185, 32, 167, 169, 223, 2, 17, 0, 0, 0, 6, 74, 15, 80, 19, 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