Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b192776da6f4f512629e11c32ed03c8ee7e9e472625f9127fb0efda6425cc9d7

Tx prefix hash: 7621e42bb24bbc6c9e40aae1a8b788396d350472e56ac1f4b5e6a85978723f2b
Tx public key: b74b09329edca8e2c2df33cbbbca1d426306c79dffc99c9e53f776545d6e2af1
Timestamp: 1699892687 Timestamp [UCT]: 2023-11-13 16:24:47 Age [y:d:h:m:s]: 01:067:07:36:32
Block: 890854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309485 RingCT/type: yes/0
Extra: 01b74b09329edca8e2c2df33cbbbca1d426306c79dffc99c9e53f776545d6e2af10211000000014b8f5122000000000000000000

1 output(s) for total of 0.685852749000 dcy

stealth address amount amount idx
00: 227f46d955588870ba79d6c61401180381c02e8f0cc8cb4e700a08b9884d73a4 0.685852749000 1346885 of 0

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": 890864, "vin": [ { "gen": { "height": 890854 } } ], "vout": [ { "amount": 685852749, "target": { "key": "227f46d955588870ba79d6c61401180381c02e8f0cc8cb4e700a08b9884d73a4" } } ], "extra": [ 1, 183, 75, 9, 50, 158, 220, 168, 226, 194, 223, 51, 203, 187, 202, 29, 66, 99, 6, 199, 157, 255, 201, 156, 158, 83, 247, 118, 84, 93, 110, 42, 241, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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