Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df73bbd45ab87c35cf50b2394e7c9464a3dfc3c5ce522a48cab08613c9f65fc9

Tx prefix hash: 0723ac35d92e978b88d99876130a354725ce96c97372c6ab538ba7225d98d71c
Tx public key: fb3a0dcab0e9c0682b50b0049ae2dd0c9f0934e0c8a09eb8e86e815abc694034
Timestamp: 1637262104 Timestamp [UCT]: 2021-11-18 19:01:44 Age [y:d:h:m:s]: 03:011:05:14:51
Block: 377153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 786749 RingCT/type: yes/0
Extra: 01fb3a0dcab0e9c0682b50b0049ae2dd0c9f0934e0c8a09eb8e86e815abc69403402110000003bb494d89c000000000000000000

1 output(s) for total of 34.541081564000 dcy

stealth address amount amount idx
00: 5c38a3bb4b8032def2645413698f11d5d063e0e4ecd845af60be6d1e1e4befc1 34.541081564000 762895 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": 377163, "vin": [ { "gen": { "height": 377153 } } ], "vout": [ { "amount": 34541081564, "target": { "key": "5c38a3bb4b8032def2645413698f11d5d063e0e4ecd845af60be6d1e1e4befc1" } } ], "extra": [ 1, 251, 58, 13, 202, 176, 233, 192, 104, 43, 80, 176, 4, 154, 226, 221, 12, 159, 9, 52, 224, 200, 160, 158, 184, 232, 110, 129, 90, 188, 105, 64, 52, 2, 17, 0, 0, 0, 59, 180, 148, 216, 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