Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf43d000b9f94ea79524ba720337555f6df5028e30ef053724b7ab3b268cd2c1

Tx prefix hash: 86dfb8005d38b42f6d04fafc47fa85ece057e52051635110403855c08e838a5a
Tx public key: 318fe22b9b2aeae548d690a18dafec804a08b3f845af3e27c1c9b307b67bc7bf
Timestamp: 1726011856 Timestamp [UCT]: 2024-09-10 23:44:16 Age [y:d:h:m:s]: 00:261:03:49:17
Block: 1107398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186529 RingCT/type: yes/0
Extra: 01318fe22b9b2aeae548d690a18dafec804a08b3f845af3e27c1c9b307b67bc7bf02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7ed240fb2ce9b655d1a8a12aafc24070850cacda5e02bdc5038c163de09a78d 0.600000000000 1585009 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": 1107408, "vin": [ { "gen": { "height": 1107398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7ed240fb2ce9b655d1a8a12aafc24070850cacda5e02bdc5038c163de09a78d" } } ], "extra": [ 1, 49, 143, 226, 43, 155, 42, 234, 229, 72, 214, 144, 161, 141, 175, 236, 128, 74, 8, 179, 248, 69, 175, 62, 39, 193, 201, 179, 7, 182, 123, 199, 191, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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