Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b137e494b0a6f898a70707472f0c9ba02774ee01d9dbd87be3cc1420bdf49c8a

Tx prefix hash: 2518bbd09af8578decede47c37f57478bbb1ada46e138a4d68b04901d18d3d09
Tx public key: 2f1a06c1c882038e33cd1651e9b7f6692ba3b9564bb091c935af5479b727a653
Timestamp: 1713823167 Timestamp [UCT]: 2024-04-22 21:59:27 Age [y:d:h:m:s]: 01:257:23:41:24
Block: 1006346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443125 RingCT/type: yes/0
Extra: 012f1a06c1c882038e33cd1651e9b7f6692ba3b9564bb091c935af5479b727a6530211000000010011055b000000000000000000

1 output(s) for total of 0.615600000000 dcy

stealth address amount amount idx
00: 9bf39f2b1cc0c551f103d5ae24b7f09ea3a01f36af1af02c633153ac9704b095 0.615600000000 1467352 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": 1006356, "vin": [ { "gen": { "height": 1006346 } } ], "vout": [ { "amount": 615600000, "target": { "key": "9bf39f2b1cc0c551f103d5ae24b7f09ea3a01f36af1af02c633153ac9704b095" } } ], "extra": [ 1, 47, 26, 6, 193, 200, 130, 3, 142, 51, 205, 22, 81, 233, 183, 246, 105, 43, 163, 185, 86, 75, 176, 145, 201, 53, 175, 84, 121, 183, 39, 166, 83, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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