Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b573dac8af8f3b22a03ac762e70f6d8e1b5d99eb4a9fa6cd7e7c71cb563764a6

Tx prefix hash: 059f41ba3719608ea083bcd5e6090f5ec06721abfe2beab98fbf534c4a0c5bde
Tx public key: 6e2db562718980273bfdafbbf89b14e26162f2db819da1231cc1246a6e849a55
Timestamp: 1729507771 Timestamp [UCT]: 2024-10-21 10:49:31 Age [y:d:h:m:s]: 00:001:12:33:26
Block: 1136338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1103 RingCT/type: yes/0
Extra: 016e2db562718980273bfdafbbf89b14e26162f2db819da1231cc1246a6e849a55021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a073c6a56963a4ff4c2c67952de3dea593769dcaa2f0b58c8bc2558549ef2664 0.600000000000 1619683 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": 1136348, "vin": [ { "gen": { "height": 1136338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a073c6a56963a4ff4c2c67952de3dea593769dcaa2f0b58c8bc2558549ef2664" } } ], "extra": [ 1, 110, 45, 181, 98, 113, 137, 128, 39, 59, 253, 175, 187, 248, 155, 20, 226, 97, 98, 242, 219, 129, 157, 161, 35, 28, 193, 36, 106, 110, 132, 154, 85, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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