Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28946db53ae66b30ba8bf8b85055e735475f9d897faa1b62910a91e2b2ecb3bc

Tx prefix hash: d5aac31ee4b882be0dd061f83154a9981a74533a6d96df9fac8995f1d8b0a369
Tx public key: 3297f3b2f9854cad97cecc91cc450e3c01780c3191fa5533a25b76293d5740d7
Timestamp: 1750912351 Timestamp [UCT]: 2025-06-26 04:32:31 Age [y:d:h:m:s]: 00:148:07:28:33
Block: 1312944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103989 RingCT/type: yes/0
Extra: 013297f3b2f9854cad97cecc91cc450e3c01780c3191fa5533a25b76293d5740d7021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 874a427e2a1ba918c8ecd4c5fe9543f2c2b6b5fffbf6c999f4a21fdbf2262930 0.600000000000 1800581 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": 1312954, "vin": [ { "gen": { "height": 1312944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "874a427e2a1ba918c8ecd4c5fe9543f2c2b6b5fffbf6c999f4a21fdbf2262930" } } ], "extra": [ 1, 50, 151, 243, 178, 249, 133, 76, 173, 151, 206, 204, 145, 204, 69, 14, 60, 1, 120, 12, 49, 145, 250, 85, 51, 162, 91, 118, 41, 61, 87, 64, 215, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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