Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc9260fc60799b2ae5e3c7c0a728d95ef5fd0ee9744e56c0dd797bd33662c208

Tx prefix hash: 92e34afaf18490b066537765fcdacfbf92140779752b4b619eca2e24296503bc
Tx public key: 22980dd582a860e0fe0ea56fb74de8d2a160c0a6d46b704ae564ed9dac4b87c3
Timestamp: 1698927786 Timestamp [UCT]: 2023-11-02 12:23:06 Age [y:d:h:m:s]: 01:193:02:49:23
Block: 883066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399033 RingCT/type: yes/0
Extra: 0122980dd582a860e0fe0ea56fb74de8d2a160c0a6d46b704ae564ed9dac4b87c302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.727839753000 dcy

stealth address amount amount idx
00: 4b20273e311dc52df7aa7d63c7c673721b51eb389d4b5e27e111fd55bf82ab5a 0.727839753000 1338748 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": 883076, "vin": [ { "gen": { "height": 883066 } } ], "vout": [ { "amount": 727839753, "target": { "key": "4b20273e311dc52df7aa7d63c7c673721b51eb389d4b5e27e111fd55bf82ab5a" } } ], "extra": [ 1, 34, 152, 13, 213, 130, 168, 96, 224, 254, 14, 165, 111, 183, 77, 232, 210, 161, 96, 192, 166, 212, 107, 112, 74, 229, 100, 237, 157, 172, 75, 135, 195, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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