Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 782e4818049eea17ad5ff3d791e06d03eac39d914bd06bc52d43bc1c8ce60031

Tx prefix hash: f55b370de8d271f10a9641f2f1e908f37fd6fbb14797a9917da06e755a359535
Tx public key: 5babd1cfe37c304b0a366cb9bc1171b4b16949037a1c664f3fce3c5f4f599ff7
Timestamp: 1706257868 Timestamp [UCT]: 2024-01-26 08:31:08 Age [y:d:h:m:s]: 01:286:11:47:47
Block: 943605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 463561 RingCT/type: yes/0
Extra: 015babd1cfe37c304b0a366cb9bc1171b4b16949037a1c664f3fce3c5f4f599ff702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 073e9ac3115c8d077d1188913bb3070f487ac5b4a40b926c054c374565628880 0.600000000000 1401813 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": 943615, "vin": [ { "gen": { "height": 943605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "073e9ac3115c8d077d1188913bb3070f487ac5b4a40b926c054c374565628880" } } ], "extra": [ 1, 91, 171, 209, 207, 227, 124, 48, 75, 10, 54, 108, 185, 188, 17, 113, 180, 177, 105, 73, 3, 122, 28, 102, 79, 63, 206, 60, 95, 79, 89, 159, 247, 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