Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d99e6f15c6c752ea636673fc975e08cc8f76bf61848e0111458b8d752c73e142

Tx prefix hash: 0869aa7db37cba226a3088d6be78d1a7cf410ba861ef87fdb855fddd4d38f36f
Tx public key: f5c2bd53ae0d346963d6225ee1d24011ce3a60fe29bcb043880afedb11f4faab
Timestamp: 1702124213 Timestamp [UCT]: 2023-12-09 12:16:53 Age [y:d:h:m:s]: 01:334:07:15:33
Block: 909349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497791 RingCT/type: yes/0
Extra: 01f5c2bd53ae0d346963d6225ee1d24011ce3a60fe29bcb043880afedb11f4faab02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5fd508403060d1dcebfaa506ddcb79a573caff106733a321f59c402d7aaa0d5 0.600000000000 1366430 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": 909359, "vin": [ { "gen": { "height": 909349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5fd508403060d1dcebfaa506ddcb79a573caff106733a321f59c402d7aaa0d5" } } ], "extra": [ 1, 245, 194, 189, 83, 174, 13, 52, 105, 99, 214, 34, 94, 225, 210, 64, 17, 206, 58, 96, 254, 41, 188, 176, 67, 136, 10, 254, 219, 17, 244, 250, 171, 2, 17, 0, 0, 0, 7, 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