Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d2732f6f32018842db51b7d5b9980208c5abf692e7dd8eaa71cab74a70ab0cc

Tx prefix hash: 354026ed99c4040660d35a0edc8c55a9a25669200acfebc2d7b2176c4924c4f4
Tx public key: 53905f06bcdb07a7cffd9bb8f89158d58fb17bf0b2184c8158536dd2996e545f
Timestamp: 1701600564 Timestamp [UCT]: 2023-12-03 10:49:24 Age [y:d:h:m:s]: 01:124:14:20:08
Block: 905011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350203 RingCT/type: yes/0
Extra: 0153905f06bcdb07a7cffd9bb8f89158d58fb17bf0b2184c8158536dd2996e545f021100000004faf35c9c000000000000000000

1 output(s) for total of 0.615634352000 dcy

stealth address amount amount idx
00: 9bd57f479984e2ebb9a2b767e88dcd2bc0928dafd499803376e9442f1d2a0f82 0.615634352000 1361834 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": 905021, "vin": [ { "gen": { "height": 905011 } } ], "vout": [ { "amount": 615634352, "target": { "key": "9bd57f479984e2ebb9a2b767e88dcd2bc0928dafd499803376e9442f1d2a0f82" } } ], "extra": [ 1, 83, 144, 95, 6, 188, 219, 7, 167, 207, 253, 155, 184, 248, 145, 88, 213, 143, 177, 123, 240, 178, 24, 76, 129, 88, 83, 109, 210, 153, 110, 84, 95, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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