Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 056f844a0abdd8b4596007bbbeac41634f7a3e302d2979d2c23733f6df4c9be4

Tx prefix hash: 3e56240871f4dfc43ccc74c313493728be74edcdca52321b01a21df9550b4671
Tx public key: 3cdda17535f0cac8771f1194a46f64f3c642348f3d9dfcf833e496eef103bc1c
Timestamp: 1579209435 Timestamp [UCT]: 2020-01-16 21:17:15 Age [y:d:h:m:s]: 04:344:05:36:31
Block: 47097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135496 RingCT/type: yes/0
Extra: 013cdda17535f0cac8771f1194a46f64f3c642348f3d9dfcf833e496eef103bc1c021100000001ff58ae94000000000000000000

1 output(s) for total of 428.498124448000 dcy

stealth address amount amount idx
00: f0cf9f6ab899617f161bd0de63ca7573ad7a77238b0473397084e3b7af739f4b 428.498124448000 86992 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": 47107, "vin": [ { "gen": { "height": 47097 } } ], "vout": [ { "amount": 428498124448, "target": { "key": "f0cf9f6ab899617f161bd0de63ca7573ad7a77238b0473397084e3b7af739f4b" } } ], "extra": [ 1, 60, 221, 161, 117, 53, 240, 202, 200, 119, 31, 17, 148, 164, 111, 100, 243, 198, 66, 52, 143, 61, 157, 252, 248, 51, 228, 150, 238, 241, 3, 188, 28, 2, 17, 0, 0, 0, 1, 255, 88, 174, 148, 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