Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7938a79749e24a2daa7e396e3d53ea7c8c235b48d3b85925eb9a10d50db6283f

Tx prefix hash: 9a3c8d67f28392b7655ea518b74604453f349eaa6cfc39b362c1a36cf9e01511
Tx public key: 417a0eabcda4304317f5b72317a53ef65876e6fc935f498296be2223e155a9af
Timestamp: 1643262800 Timestamp [UCT]: 2022-01-27 05:53:20 Age [y:d:h:m:s]: 03:013:07:29:45
Block: 426143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 788679 RingCT/type: yes/0
Extra: 01417a0eabcda4304317f5b72317a53ef65876e6fc935f498296be2223e155a9af021100000006a511e5b4000000000000000000

1 output(s) for total of 23.769040703000 dcy

stealth address amount amount idx
00: a751b59f3b4e843e5f9b5a49aebb4b3d3b6bf2269bb0640acd7932f16e9e539f 23.769040703000 834936 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": 426153, "vin": [ { "gen": { "height": 426143 } } ], "vout": [ { "amount": 23769040703, "target": { "key": "a751b59f3b4e843e5f9b5a49aebb4b3d3b6bf2269bb0640acd7932f16e9e539f" } } ], "extra": [ 1, 65, 122, 14, 171, 205, 164, 48, 67, 23, 245, 183, 35, 23, 165, 62, 246, 88, 118, 230, 252, 147, 95, 73, 130, 150, 190, 34, 35, 225, 85, 169, 175, 2, 17, 0, 0, 0, 6, 165, 17, 229, 180, 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