Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51e25a1345b9016e845dbb4684af0a0bfa466b461f04093405611e29cfbcb28f

Tx prefix hash: 691d8318a1bed6538b69553627f3bb3d4477c87544c5d655b9b5fe3fb40f9946
Tx public key: b75a5e6c0ba2f56401ce0d45b8d41fc787cdde8c0393e575edb0a8b46c2a134b
Timestamp: 1737910832 Timestamp [UCT]: 2025-01-26 17:00:32 Age [y:d:h:m:s]: 00:141:19:40:33
Block: 1205885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101075 RingCT/type: yes/0
Extra: 01b75a5e6c0ba2f56401ce0d45b8d41fc787cdde8c0393e575edb0a8b46c2a134b02110000000d2609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8129d2011a61f81f69012436773594d3fa322701a438c70ecc2d12b52b8a620 0.600000000000 1692584 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": 1205895, "vin": [ { "gen": { "height": 1205885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8129d2011a61f81f69012436773594d3fa322701a438c70ecc2d12b52b8a620" } } ], "extra": [ 1, 183, 90, 94, 108, 11, 162, 245, 100, 1, 206, 13, 69, 184, 212, 31, 199, 135, 205, 222, 140, 3, 147, 229, 117, 237, 176, 168, 180, 108, 42, 19, 75, 2, 17, 0, 0, 0, 13, 38, 9, 179, 160, 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