Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5427e535ef128d55df7e3c8b969fc964d9e6cc87cabfb807406c1e94ba15e72

Tx prefix hash: 1324a99e7493088955b9d95f886f1ca460d9aebe867b8e83b1ee92edc7ffeb5f
Tx public key: 46914d16f3f9145b06b63629f3fceedcaee1156fe91a548a16a97a0a7c46beb7
Timestamp: 1676402403 Timestamp [UCT]: 2023-02-14 19:20:03 Age [y:d:h:m:s]: 01:316:19:49:01
Block: 697006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487363 RingCT/type: yes/0
Extra: 0146914d16f3f9145b06b63629f3fceedcaee1156fe91a548a16a97a0a7c46beb7021100000008835e4d22000000000000000000

1 output(s) for total of 3.009744980000 dcy

stealth address amount amount idx
00: 8b78cc53b6707f830e7fc36994cc5280126f9a08fd26e0c8cc3c6c151951a82e 3.009744980000 1140071 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": 697016, "vin": [ { "gen": { "height": 697006 } } ], "vout": [ { "amount": 3009744980, "target": { "key": "8b78cc53b6707f830e7fc36994cc5280126f9a08fd26e0c8cc3c6c151951a82e" } } ], "extra": [ 1, 70, 145, 77, 22, 243, 249, 20, 91, 6, 182, 54, 41, 243, 252, 238, 220, 174, 225, 21, 111, 233, 26, 84, 138, 22, 169, 122, 10, 124, 70, 190, 183, 2, 17, 0, 0, 0, 8, 131, 94, 77, 34, 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