Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cf9bff8176d3ace701b76934180a42aeeebeca18ee370b803ac95c762cf7b5d

Tx prefix hash: 8b840b62e556a4bd489f006e632d152bb22652c05cb9e32a73074d2ffdc0e27e
Tx public key: bbd2dee5e59dcd9a3df6dd4ee8fb2f121a93394945fecdf1764d9da43dcd68de
Timestamp: 1737986454 Timestamp [UCT]: 2025-01-27 14:00:54 Age [y:d:h:m:s]: 01:004:01:54:31
Block: 1206275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261447 RingCT/type: yes/0
Extra: 01bbd2dee5e59dcd9a3df6dd4ee8fb2f121a93394945fecdf1764d9da43dcd68de021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a50f36804e7c0dc157ba663af493cc32b219ec0d19b6f9c4533bb686eb14142a 0.600000000000 1692978 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": 1206285, "vin": [ { "gen": { "height": 1206275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a50f36804e7c0dc157ba663af493cc32b219ec0d19b6f9c4533bb686eb14142a" } } ], "extra": [ 1, 187, 210, 222, 229, 229, 157, 205, 154, 61, 246, 221, 78, 232, 251, 47, 18, 26, 147, 57, 73, 69, 254, 205, 241, 118, 77, 157, 164, 61, 205, 104, 222, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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