Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96b1052feaa7e6852d031f7635631081efcfd68f188fa8b6be17bb35c9f1ebae

Tx prefix hash: 0b8fc52f85c26e1fb0f8030a7610613e1adb6b439c872a8cc4ede6d1db1edbba
Tx public key: 6c8259c176475a58059ed1061c8a2b4e75015b91f6c1c8dc1ebd83b6e2dd11b4
Timestamp: 1699431678 Timestamp [UCT]: 2023-11-08 08:21:18 Age [y:d:h:m:s]: 01:133:13:31:35
Block: 887034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356660 RingCT/type: yes/0
Extra: 016c8259c176475a58059ed1061c8a2b4e75015b91f6c1c8dc1ebd83b6e2dd11b402110000000375e3f0e9000000000000000000

1 output(s) for total of 0.706135645000 dcy

stealth address amount amount idx
00: 4cf461233c0849078eac94c4d5fc028aadbb24bbaa1e2e12e01250935efa598d 0.706135645000 1342885 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": 887044, "vin": [ { "gen": { "height": 887034 } } ], "vout": [ { "amount": 706135645, "target": { "key": "4cf461233c0849078eac94c4d5fc028aadbb24bbaa1e2e12e01250935efa598d" } } ], "extra": [ 1, 108, 130, 89, 193, 118, 71, 90, 88, 5, 158, 209, 6, 28, 138, 43, 78, 117, 1, 91, 145, 246, 193, 200, 220, 30, 189, 131, 182, 226, 221, 17, 180, 2, 17, 0, 0, 0, 3, 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