Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ad1fa5297ca3fd46fee20a2b8fa0f4bd6a688ababbccf91f8406a29ead221a8

Tx prefix hash: a320773c5b76acdd6e6e2c30861f783a5ff6db7af0f11ea2fb2f032535335838
Tx public key: 0d55d45e8cf8bc6899e9fd21f1559b370a30a66c145f0cdb47f58b9ff3fb89db
Timestamp: 1698835370 Timestamp [UCT]: 2023-11-01 10:42:50 Age [y:d:h:m:s]: 02:010:13:50:39
Block: 882307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527138 RingCT/type: yes/0
Extra: 010d55d45e8cf8bc6899e9fd21f1559b370a30a66c145f0cdb47f58b9ff3fb89db02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.732066705000 dcy

stealth address amount amount idx
00: 9d4bab7d731eccbcc5ebbfabf9c418c8980b0f40921670f101d6768da13142a2 0.732066705000 1337961 of 0

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": 882317, "vin": [ { "gen": { "height": 882307 } } ], "vout": [ { "amount": 732066705, "target": { "key": "9d4bab7d731eccbcc5ebbfabf9c418c8980b0f40921670f101d6768da13142a2" } } ], "extra": [ 1, 13, 85, 212, 94, 140, 248, 188, 104, 153, 233, 253, 33, 241, 85, 155, 55, 10, 48, 166, 108, 20, 95, 12, 219, 71, 245, 139, 159, 243, 251, 137, 219, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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