Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f789c4273de71866dce53655ca2fbcd72db656b056ea91d2e5a3ee90b80f31ab

Tx prefix hash: 3294f1bfa5a73239dbfd847102e2a5d5a3a5addf26fce955c15be010178f878b
Tx public key: 82fc0be3ee8d2c48f0bd13aa22d4a1afbbe245dfc446ab917ee2420a169614a6
Timestamp: 1722180992 Timestamp [UCT]: 2024-07-28 15:36:32 Age [y:d:h:m:s]: 00:238:08:36:50
Block: 1075637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170243 RingCT/type: yes/0
Extra: 0182fc0be3ee8d2c48f0bd13aa22d4a1afbbe245dfc446ab917ee2420a169614a602110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90684c66c040760e071645292e7dd964d417646b1a8183b7fb40714cf9f95225 0.600000000000 1548166 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": 1075647, "vin": [ { "gen": { "height": 1075637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90684c66c040760e071645292e7dd964d417646b1a8183b7fb40714cf9f95225" } } ], "extra": [ 1, 130, 252, 11, 227, 238, 141, 44, 72, 240, 189, 19, 170, 34, 212, 161, 175, 187, 226, 69, 223, 196, 70, 171, 145, 126, 226, 66, 10, 22, 150, 20, 166, 2, 17, 0, 0, 0, 7, 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