Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47693db031e1d82a061f86b6ec4706d6e905ab2b5d88d2a49fea518cd1dbe59a

Tx prefix hash: 0dc87328dae4e281ca8cd0729cac7067f3d2af5ff5c2eccb9b6a75c78eed6bac
Tx public key: 20912373431bdd9c960ce78902863f5857cda4d17f45c70afd7688ed2db16eef
Timestamp: 1719870498 Timestamp [UCT]: 2024-07-01 21:48:18 Age [y:d:h:m:s]: 01:128:01:40:32
Block: 1056475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350056 RingCT/type: yes/0
Extra: 0120912373431bdd9c960ce78902863f5857cda4d17f45c70afd7688ed2db16eef0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b8a0cdd639e2fbc597f9f0161727f35e68a121f83a3e08f3f28f59e308a2c08 0.600000000000 1526888 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": 1056485, "vin": [ { "gen": { "height": 1056475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b8a0cdd639e2fbc597f9f0161727f35e68a121f83a3e08f3f28f59e308a2c08" } } ], "extra": [ 1, 32, 145, 35, 115, 67, 27, 221, 156, 150, 12, 231, 137, 2, 134, 63, 88, 87, 205, 164, 209, 127, 69, 199, 10, 253, 118, 136, 237, 45, 177, 110, 239, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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