Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc0addb1fcbe74a1b71b5cc7d2c3c76b86e7637d0f0d1eaf80bbf485ffc847cf

Tx prefix hash: 8362a8cb6c28d1693bfc510092134539631d79d73db5e7815ed8dc29ad8e20fe
Tx public key: 0c7dd717e50b4744e3d0e70e7e47cf4c7dc656ec4ad8dd5ff9908e12515d6530
Timestamp: 1719630430 Timestamp [UCT]: 2024-06-29 03:07:10 Age [y:d:h:m:s]: 01:177:15:27:38
Block: 1054487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385553 RingCT/type: yes/0
Extra: 010c7dd717e50b4744e3d0e70e7e47cf4c7dc656ec4ad8dd5ff9908e12515d653002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1b70b7551453b3979d6bbb919769b03d0d8b5f91aea23b0e327ebabd9d263da 0.600000000000 1524850 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": 1054497, "vin": [ { "gen": { "height": 1054487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1b70b7551453b3979d6bbb919769b03d0d8b5f91aea23b0e327ebabd9d263da" } } ], "extra": [ 1, 12, 125, 215, 23, 229, 11, 71, 68, 227, 208, 231, 14, 126, 71, 207, 76, 125, 198, 86, 236, 74, 216, 221, 95, 249, 144, 142, 18, 81, 93, 101, 48, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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