Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f55fb46989bb797720030bc50835bb4842bc128001a64a6c27880135ebc6c4b

Tx prefix hash: e5045cad706ddc35b386b1e2dfaf5cf3d6bead455ab5a482d5b791a1735b4c2f
Tx public key: f231a9204fabc31a28dfce9a6b6369364831cc72d8963f6431bb1d5ee7d4e5a7
Timestamp: 1724030892 Timestamp [UCT]: 2024-08-19 01:28:12 Age [y:d:h:m:s]: 00:210:00:25:43
Block: 1090978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149967 RingCT/type: yes/0
Extra: 01f231a9204fabc31a28dfce9a6b6369364831cc72d8963f6431bb1d5ee7d4e5a7021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e1f9a3d65f234edcbca45326600c82b8063f8e4aa6981cf53eadc1dcf2e0344 0.600000000000 1565603 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": 1090988, "vin": [ { "gen": { "height": 1090978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e1f9a3d65f234edcbca45326600c82b8063f8e4aa6981cf53eadc1dcf2e0344" } } ], "extra": [ 1, 242, 49, 169, 32, 79, 171, 195, 26, 40, 223, 206, 154, 107, 99, 105, 54, 72, 49, 204, 114, 216, 150, 63, 100, 49, 187, 29, 94, 231, 212, 229, 167, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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