Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5697d6fb9174de0eb043a4d1fdc5dbd1da048142407b2c5eeadf2e00c5c2cdd5

Tx prefix hash: 00b48eb395099789c6948a2f8d299be1e4f41c0776a471047598524daddcc827
Tx public key: a4d43f2fb5f285e4a085849f06089dbe35511a3bcfaa3e11e41fe7afdd821b43
Timestamp: 1742203735 Timestamp [UCT]: 2025-03-17 09:28:55 Age [y:d:h:m:s]: 00:248:18:35:27
Block: 1241177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175515 RingCT/type: yes/0
Extra: 01a4d43f2fb5f285e4a085849f06089dbe35511a3bcfaa3e11e41fe7afdd821b43021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 811b0ecbc475bd9fca9a4a0367be47991c7b1ac4665372257a96e599a000d179 0.600000000000 1728150 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": 1241187, "vin": [ { "gen": { "height": 1241177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "811b0ecbc475bd9fca9a4a0367be47991c7b1ac4665372257a96e599a000d179" } } ], "extra": [ 1, 164, 212, 63, 47, 181, 242, 133, 228, 160, 133, 132, 159, 6, 8, 157, 190, 53, 81, 26, 59, 207, 170, 62, 17, 228, 31, 231, 175, 221, 130, 27, 67, 2, 17, 0, 0, 0, 2, 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