Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf08b520d05fab1fb52c66bb835b7a01543d6d47fb26ef5146945b112819ae52

Tx prefix hash: 2750b0554b07e6b8a96534b6bef6b4ea988efd2b7103babd7f8cdf39d84595bc
Tx public key: 75b2ce9cc662030067eef78bc88a173a4ceda195b4a410fddd351838cb3dfe7a
Timestamp: 1737156473 Timestamp [UCT]: 2025-01-17 23:27:53 Age [y:d:h:m:s]: 00:152:06:39:01
Block: 1199638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108512 RingCT/type: yes/0
Extra: 0175b2ce9cc662030067eef78bc88a173a4ceda195b4a410fddd351838cb3dfe7a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c11d8f363b9c8e4e58ba67f4d4adf8f382640d7669c809bb80291e3703cf5f01 0.600000000000 1686271 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": 1199648, "vin": [ { "gen": { "height": 1199638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c11d8f363b9c8e4e58ba67f4d4adf8f382640d7669c809bb80291e3703cf5f01" } } ], "extra": [ 1, 117, 178, 206, 156, 198, 98, 3, 0, 103, 238, 247, 139, 200, 138, 23, 58, 76, 237, 161, 149, 180, 164, 16, 253, 221, 53, 24, 56, 203, 61, 254, 122, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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