Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0816c6f14210414e873da5d1d945ead97901dd8e0214229b9ebaf8ee598dc6ec

Tx prefix hash: d97b35a4b3ee70d3b666af1bb4b63a9c654262d64b5da3199f76d78cd61a5beb
Tx public key: d6a885543d3ebc32314de30e5078f55f371f311c06a2979b302eeecd5be5bb22
Timestamp: 1703253428 Timestamp [UCT]: 2023-12-22 13:57:08 Age [y:d:h:m:s]: 01:335:03:51:46
Block: 918719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498385 RingCT/type: yes/0
Extra: 01d6a885543d3ebc32314de30e5078f55f371f311c06a2979b302eeecd5be5bb220211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8e5ff5ea016c019e4a7d81982a611a6f42c738cc41069dcf8d8331515b03518 0.600000000000 1376377 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": 918729, "vin": [ { "gen": { "height": 918719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8e5ff5ea016c019e4a7d81982a611a6f42c738cc41069dcf8d8331515b03518" } } ], "extra": [ 1, 214, 168, 133, 84, 61, 62, 188, 50, 49, 77, 227, 14, 80, 120, 245, 95, 55, 31, 49, 28, 6, 162, 151, 155, 48, 46, 238, 205, 91, 229, 187, 34, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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