Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d841ab02ea0849caf4c152c0700a4e42747203f9681dfcfe9da242f846c959d5

Tx prefix hash: d906974cbb467fc7bffc19fea427db84e9cec399c5c741ba1bee3d0a3a467151
Tx public key: 85d51ea8da7765fa8a6987153fe73db699e88f5b3073574e01c18584be9406d1
Timestamp: 1685851363 Timestamp [UCT]: 2023-06-04 04:02:43 Age [y:d:h:m:s]: 02:016:21:29:20
Block: 774688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 534047 RingCT/type: yes/0
Extra: 0185d51ea8da7765fa8a6987153fe73db699e88f5b3073574e01c18584be9406d1021100000001faf35c9c000000000000000000

1 output(s) for total of 1.663938363000 dcy

stealth address amount amount idx
00: 8d95c5e48a5eb3d48c1babc39a891b8f0a4e1e72ffff7b7dad367cc431060fe3 1.663938363000 1224173 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": 774698, "vin": [ { "gen": { "height": 774688 } } ], "vout": [ { "amount": 1663938363, "target": { "key": "8d95c5e48a5eb3d48c1babc39a891b8f0a4e1e72ffff7b7dad367cc431060fe3" } } ], "extra": [ 1, 133, 213, 30, 168, 218, 119, 101, 250, 138, 105, 135, 21, 63, 231, 61, 182, 153, 232, 143, 91, 48, 115, 87, 78, 1, 193, 133, 132, 190, 148, 6, 209, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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