Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54a05722cdba4f4179f601cd38010abbf2f04949208262b8fbcc478a5c99e271

Tx prefix hash: 86e7a11ca350ee7aaebd54a6defed2b093d78c09ddf855e37b79b5ff87960744
Tx public key: f4c878c9f226a45f1d3956d55e8abc8c5ff9c243ec02c2a039c3a787fc6b99a6
Timestamp: 1745715163 Timestamp [UCT]: 2025-04-27 00:52:43 Age [y:d:h:m:s]: 00:206:23:36:40
Block: 1270229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145654 RingCT/type: yes/0
Extra: 01f4c878c9f226a45f1d3956d55e8abc8c5ff9c243ec02c2a039c3a787fc6b99a602110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4af6dd8100f8ce36de192d80fc20ef50c250ce13add98ebd458ea183ba6096fe 0.600000000000 1757470 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": 1270239, "vin": [ { "gen": { "height": 1270229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4af6dd8100f8ce36de192d80fc20ef50c250ce13add98ebd458ea183ba6096fe" } } ], "extra": [ 1, 244, 200, 120, 201, 242, 38, 164, 95, 29, 57, 86, 213, 94, 138, 188, 140, 95, 249, 194, 67, 236, 2, 194, 160, 57, 195, 167, 135, 252, 107, 153, 166, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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