Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b5be724c4251a44b6b1762bc67d69b62087c4b6feff1650033f0ecb1b816663

Tx prefix hash: b81b2d4e91e661bcf4ba0d3c1bdff846ae2ed5cf4a3cc8024a8d416127a57ddc
Tx public key: 586bfd256e6d0a21c242d40727cc5f878e7f48746d4c15c89603942d87632270
Timestamp: 1710177469 Timestamp [UCT]: 2024-03-11 17:17:49 Age [y:d:h:m:s]: 01:023:14:59:45
Block: 976137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277862 RingCT/type: yes/0
Extra: 01586bfd256e6d0a21c242d40727cc5f878e7f48746d4c15c89603942d876322700211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fa69bfc366a05ad35bc08d05ffc51e21550b6ab9adfc6e693091e4e5942c2f0 0.600000000000 1436126 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": 976147, "vin": [ { "gen": { "height": 976137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fa69bfc366a05ad35bc08d05ffc51e21550b6ab9adfc6e693091e4e5942c2f0" } } ], "extra": [ 1, 88, 107, 253, 37, 110, 109, 10, 33, 194, 66, 212, 7, 39, 204, 95, 135, 142, 127, 72, 116, 109, 76, 21, 200, 150, 3, 148, 45, 135, 99, 34, 112, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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