Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1324d06d3da0b85eed2c0f4a12c219ed1b5a6ac5427f3d7a43925aec2e255df2

Tx prefix hash: 03d16348ec13dc08025c308aa69cd7189955a54b60f0b547e91aa7956cd713ae
Tx public key: 0670943d065c4f2fe9ef66e8562a9dc163982cc47f12de722c512941a11b226a
Timestamp: 1730111874 Timestamp [UCT]: 2024-10-28 10:37:54 Age [y:d:h:m:s]: 00:159:05:11:30
Block: 1141323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113614 RingCT/type: yes/0
Extra: 010670943d065c4f2fe9ef66e8562a9dc163982cc47f12de722c512941a11b226a021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ae957c4db73983f4d835f1f779aa81509170fb549dce19e63457565e067841f 0.600000000000 1625130 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": 1141333, "vin": [ { "gen": { "height": 1141323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ae957c4db73983f4d835f1f779aa81509170fb549dce19e63457565e067841f" } } ], "extra": [ 1, 6, 112, 148, 61, 6, 92, 79, 47, 233, 239, 102, 232, 86, 42, 157, 193, 99, 152, 44, 196, 127, 18, 222, 114, 44, 81, 41, 65, 161, 27, 34, 106, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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