Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98f431787d42c027957b54dc2d85eb63878b7417f5df64ee630b052eee161fbd

Tx prefix hash: 0d578d2922e02c4670866a219380d1419aa0cf626bbe9b457760feee27c35608
Tx public key: 8a2e39b0ad735f67d99a15b1d94cb062f1c67e308edc4fb526349b64a9b2c664
Timestamp: 1745631252 Timestamp [UCT]: 2025-04-26 01:34:12 Age [y:d:h:m:s]: 00:209:15:21:03
Block: 1269519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147560 RingCT/type: yes/0
Extra: 018a2e39b0ad735f67d99a15b1d94cb062f1c67e308edc4fb526349b64a9b2c66402110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffbc860bd3e69434746958a49f234a8be887a348d45dec36bdcdca9c624f3cc8 0.600000000000 1756758 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": 1269529, "vin": [ { "gen": { "height": 1269519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffbc860bd3e69434746958a49f234a8be887a348d45dec36bdcdca9c624f3cc8" } } ], "extra": [ 1, 138, 46, 57, 176, 173, 115, 95, 103, 217, 154, 21, 177, 217, 76, 176, 98, 241, 198, 126, 48, 142, 220, 79, 181, 38, 52, 155, 100, 169, 178, 198, 100, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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