Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1b1be62e187ee84f8d0edced53264090fb56781d69af527483da78283fd80ca

Tx prefix hash: 81fdff86ad61f11759fa54637e7f054d6d55b86981b623a83d42e7f3d4d8236b
Tx public key: 7bdbeefd11db4fa1d1badf2dd8155ad3a253290a67ab468905e2a620c1f59e71
Timestamp: 1727360544 Timestamp [UCT]: 2024-09-26 14:22:24 Age [y:d:h:m:s]: 00:149:14:10:35
Block: 1118583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106676 RingCT/type: yes/0
Extra: 017bdbeefd11db4fa1d1badf2dd8155ad3a253290a67ab468905e2a620c1f59e71021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20f40217d66a3cc4d81ba2e2e843b19defa8ed3d656caa13dccbe5b0da4d7fca 0.600000000000 1599824 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": 1118593, "vin": [ { "gen": { "height": 1118583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20f40217d66a3cc4d81ba2e2e843b19defa8ed3d656caa13dccbe5b0da4d7fca" } } ], "extra": [ 1, 123, 219, 238, 253, 17, 219, 79, 161, 209, 186, 223, 45, 216, 21, 90, 211, 162, 83, 41, 10, 103, 171, 70, 137, 5, 226, 166, 32, 193, 245, 158, 113, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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