Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb5ba8bfc1523610f98ec6e2982c1027dae9419b5cfa8135fd5bc9cc5576646a

Tx prefix hash: bf4adeb016bc306de35750a0a22dd51698d3fe1704bd896982e74322714fc3ba
Tx public key: 77d897e2c35ebac6d7527ebcb0ceced34af118a50c90ca2b057975b2923ea31d
Timestamp: 1736908253 Timestamp [UCT]: 2025-01-15 02:30:53 Age [y:d:h:m:s]: 00:153:14:07:22
Block: 1197583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109486 RingCT/type: yes/0
Extra: 0177d897e2c35ebac6d7527ebcb0ceced34af118a50c90ca2b057975b2923ea31d021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d6aee4e8a8e501f360a9decd47ecf74e6d1339cd44c9c0ab2c94c6d6b2a67b5 0.600000000000 1684196 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": 1197593, "vin": [ { "gen": { "height": 1197583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d6aee4e8a8e501f360a9decd47ecf74e6d1339cd44c9c0ab2c94c6d6b2a67b5" } } ], "extra": [ 1, 119, 216, 151, 226, 195, 94, 186, 198, 215, 82, 126, 188, 176, 206, 206, 211, 74, 241, 24, 165, 12, 144, 202, 43, 5, 121, 117, 178, 146, 62, 163, 29, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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