Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 904bb6d156362733089de9167fe5ad1bc211c465c788210e04fc6842fe03304e

Tx prefix hash: 800cccce743c9a9bf0b93208d45ba9ad25f5bb8f5f87dd8c0409ca64a12b1a05
Tx public key: fe277ae35474fce90b0b9302de5f4d5cf56691c716a614d3973169a4ccc8f0a1
Timestamp: 1706035872 Timestamp [UCT]: 2024-01-23 18:51:12 Age [y:d:h:m:s]: 01:085:15:32:09
Block: 941754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322324 RingCT/type: yes/0
Extra: 01fe277ae35474fce90b0b9302de5f4d5cf56691c716a614d3973169a4ccc8f0a102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 285b2f02dcb10c9935ec405afc26d7e959f8a82527262c3a8c11c213eebbef6e 0.600000000000 1399910 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": 941764, "vin": [ { "gen": { "height": 941754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "285b2f02dcb10c9935ec405afc26d7e959f8a82527262c3a8c11c213eebbef6e" } } ], "extra": [ 1, 254, 39, 122, 227, 84, 116, 252, 233, 11, 11, 147, 2, 222, 95, 77, 92, 245, 102, 145, 199, 22, 166, 20, 211, 151, 49, 105, 164, 204, 200, 240, 161, 2, 17, 0, 0, 0, 1, 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