Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8d48300677fcc193807044f0b123716da16a78c919a95c705227c6d7cfb7279

Tx prefix hash: 828c4da223f6603c7cf58850602fe8d11152c59410383d96cc2cb9af2c4099b0
Tx public key: 2b20f830f29e24204d69cfd3b781939494196bf21cc8e716d37a255f8bf960a8
Timestamp: 1698743009 Timestamp [UCT]: 2023-10-31 09:03:29 Age [y:d:h:m:s]: 01:168:00:17:07
Block: 881538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381075 RingCT/type: yes/0
Extra: 012b20f830f29e24204d69cfd3b781939494196bf21cc8e716d37a255f8bf960a802110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.736374384000 dcy

stealth address amount amount idx
00: 33175b4ff769a5e1606f9e37b14befb43a05edec6d24e3d32e58cd552e4d75c7 0.736374384000 1337132 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": 881548, "vin": [ { "gen": { "height": 881538 } } ], "vout": [ { "amount": 736374384, "target": { "key": "33175b4ff769a5e1606f9e37b14befb43a05edec6d24e3d32e58cd552e4d75c7" } } ], "extra": [ 1, 43, 32, 248, 48, 242, 158, 36, 32, 77, 105, 207, 211, 183, 129, 147, 148, 148, 25, 107, 242, 28, 200, 231, 22, 211, 122, 37, 95, 139, 249, 96, 168, 2, 17, 0, 0, 0, 13, 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