Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 931fa74aec74f22d27ebd96086895458caa2d22960d3f9b521852c18a2ebcde3

Tx prefix hash: 084b003ce213ff90add6c715dadfd2027ce1a0ab1f332b1c308937bd3f7ad4dd
Tx public key: 32a63beb06c7af88cbd57749b74f8f2d2b57da58d1a66edfb23d096bc436c589
Timestamp: 1727438898 Timestamp [UCT]: 2024-09-27 12:08:18 Age [y:d:h:m:s]: 00:117:03:56:17
Block: 1119229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83723 RingCT/type: yes/0
Extra: 0132a63beb06c7af88cbd57749b74f8f2d2b57da58d1a66edfb23d096bc436c58902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 645c2536fff42eab0432c8454399ac873fea3469fe8a3fa75c2470f66a26a7dd 0.600000000000 1600710 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": 1119239, "vin": [ { "gen": { "height": 1119229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "645c2536fff42eab0432c8454399ac873fea3469fe8a3fa75c2470f66a26a7dd" } } ], "extra": [ 1, 50, 166, 59, 235, 6, 199, 175, 136, 203, 213, 119, 73, 183, 79, 143, 45, 43, 87, 218, 88, 209, 166, 110, 223, 178, 61, 9, 107, 196, 54, 197, 137, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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