Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 871c2f4282cd2ba1a517df4a4c556fc577b2ee90fb1c7c9f10f9724e8e69e01e

Tx prefix hash: 2d28b4cfb2426f23f41142cf28bb5d98d00cae64a4c75cc164b2e472dcf33f05
Tx public key: ecf1b19d091c5bf6ca8fbc6f33606574a23c808dab28f8eaeca443590015fb29
Timestamp: 1741002988 Timestamp [UCT]: 2025-03-03 11:56:28 Age [y:d:h:m:s]: 00:258:23:23:33
Block: 1231221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182835 RingCT/type: yes/0
Extra: 01ecf1b19d091c5bf6ca8fbc6f33606574a23c808dab28f8eaeca443590015fb290211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa1a6ed3ec52d2d31612b4d87986a010d07bd017368d330926e251b702945b59 0.600000000000 1718126 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": 1231231, "vin": [ { "gen": { "height": 1231221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa1a6ed3ec52d2d31612b4d87986a010d07bd017368d330926e251b702945b59" } } ], "extra": [ 1, 236, 241, 177, 157, 9, 28, 91, 246, 202, 143, 188, 111, 51, 96, 101, 116, 162, 60, 128, 141, 171, 40, 248, 234, 236, 164, 67, 89, 0, 21, 251, 41, 2, 17, 0, 0, 0, 6, 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