Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94414f706b82e7de20b3822e5604387bb4aafc4c0c9d437c572acd85e7d37343

Tx prefix hash: cd6e3606dcb87b82ec193598900ce80a49f4b60c0ced12c072344710547c0ab0
Tx public key: a1c4db1d7c146f25dfa79af8cef73bef3e29d19fcdc236448686ff6479c80ef8
Timestamp: 1725391020 Timestamp [UCT]: 2024-09-03 19:17:00 Age [y:d:h:m:s]: 00:119:18:04:50
Block: 1102254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85649 RingCT/type: yes/0
Extra: 01a1c4db1d7c146f25dfa79af8cef73bef3e29d19fcdc236448686ff6479c80ef802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cf2d91ab0f6f9810ce58234696ad91d3d1b0ab17f4b067a053682d1095bb6ad 0.600000000000 1578617 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": 1102264, "vin": [ { "gen": { "height": 1102254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cf2d91ab0f6f9810ce58234696ad91d3d1b0ab17f4b067a053682d1095bb6ad" } } ], "extra": [ 1, 161, 196, 219, 29, 124, 20, 111, 37, 223, 167, 154, 248, 206, 247, 59, 239, 62, 41, 209, 159, 205, 194, 54, 68, 134, 134, 255, 100, 121, 200, 14, 248, 2, 17, 0, 0, 0, 3, 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