Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce7c725169984cf49941b2c292573bdb425130843b8de19e907f88c69d92a2b4

Tx prefix hash: d2840bbd1de9ca2cdf3d7912f0450654b607b2fdd09cf51184720df33e8ecb8e
Tx public key: 5298301ad6577bdf4570fda72d609f0065d4ef7cab33c4c8224c17954fb9dffc
Timestamp: 1709404573 Timestamp [UCT]: 2024-03-02 18:36:13 Age [y:d:h:m:s]: 01:112:01:26:57
Block: 969725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340922 RingCT/type: yes/0
Extra: 015298301ad6577bdf4570fda72d609f0065d4ef7cab33c4c8224c17954fb9dffc02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 681899c9a1b7e2dccb4ec2cdb654c7425b43d6da929bfb8549bec47988c402f9 0.600000000000 1429564 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": 969735, "vin": [ { "gen": { "height": 969725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "681899c9a1b7e2dccb4ec2cdb654c7425b43d6da929bfb8549bec47988c402f9" } } ], "extra": [ 1, 82, 152, 48, 26, 214, 87, 123, 223, 69, 112, 253, 167, 45, 96, 159, 0, 101, 212, 239, 124, 171, 51, 196, 200, 34, 76, 23, 149, 79, 185, 223, 252, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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