Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f13d91617e0421c72cc7232b6ddca6dbe339054dddf4eb9edcede3b1afc2b2b

Tx prefix hash: 2b1f0c94d9ad575f5c3e3d3f3a08e4b4758fb3d61309f21653b40030df89f1b9
Tx public key: 8783460c307cfdfb377736e5b22b10d7556baa5d53cb7aa36c95ba412950e3c0
Timestamp: 1670937412 Timestamp [UCT]: 2022-12-13 13:16:52 Age [y:d:h:m:s]: 02:171:20:33:03
Block: 651696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 644561 RingCT/type: yes/0
Extra: 018783460c307cfdfb377736e5b22b10d7556baa5d53cb7aa36c95ba412950e3c00211000000077e406890000000000000000000

1 output(s) for total of 4.252659431000 dcy

stealth address amount amount idx
00: c62a32396049b6a4734ae6be7849b4484067c308f3192fb4fc7d2d00c5b09b28 4.252659431000 1092113 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": 651706, "vin": [ { "gen": { "height": 651696 } } ], "vout": [ { "amount": 4252659431, "target": { "key": "c62a32396049b6a4734ae6be7849b4484067c308f3192fb4fc7d2d00c5b09b28" } } ], "extra": [ 1, 135, 131, 70, 12, 48, 124, 253, 251, 55, 119, 54, 229, 178, 43, 16, 215, 85, 107, 170, 93, 83, 203, 122, 163, 108, 149, 186, 65, 41, 80, 227, 192, 2, 17, 0, 0, 0, 7, 126, 64, 104, 144, 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