Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73ae652de450d60c9c154b62a4c2a2e531810f92e726c8ffddcc32c58ce6317d

Tx prefix hash: 29b6df1dc163cbcfac8cdb01f62b070553f0ecfeccfb8d0010afd63cf4f3c1a9
Tx public key: cc532501c3306462164e06f57ee5777080b903e237428c47ffd2c031063f5361
Timestamp: 1698624106 Timestamp [UCT]: 2023-10-30 00:01:46 Age [y:d:h:m:s]: 02:006:12:58:00
Block: 880553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524245 RingCT/type: yes/0
Extra: 01cc532501c3306462164e06f57ee5777080b903e237428c47ffd2c031063f5361021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.741929070000 dcy

stealth address amount amount idx
00: ff7eb2985a941c676a3b215eac850ea042df4d013f54687a9ec175135c62e7c8 0.741929070000 1336111 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": 880563, "vin": [ { "gen": { "height": 880553 } } ], "vout": [ { "amount": 741929070, "target": { "key": "ff7eb2985a941c676a3b215eac850ea042df4d013f54687a9ec175135c62e7c8" } } ], "extra": [ 1, 204, 83, 37, 1, 195, 48, 100, 98, 22, 78, 6, 245, 126, 229, 119, 112, 128, 185, 3, 226, 55, 66, 140, 71, 255, 210, 192, 49, 6, 63, 83, 97, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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