Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d6541b23bb2d51c0d55d48d5e69d651e14f1c078885092606a14d87a915c75f

Tx prefix hash: 38ca9605d9830b5ebf3f5435db095ef37ddc49ceb4d3945785d130515b32a644
Tx public key: f1fe2ce55cf874da32ccec4dceae7c26632e8c70a49afc2d693295a377f117d7
Timestamp: 1713754675 Timestamp [UCT]: 2024-04-22 02:57:55 Age [y:d:h:m:s]: 00:206:07:01:08
Block: 1005771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147680 RingCT/type: yes/0
Extra: 01f1fe2ce55cf874da32ccec4dceae7c26632e8c70a49afc2d693295a377f117d70211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40b81bc6b2ecd6fd8bd4b5efdbd9ee73981dd46aa0017fe157f9064c9b1daa7a 0.600000000000 1466571 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": 1005781, "vin": [ { "gen": { "height": 1005771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40b81bc6b2ecd6fd8bd4b5efdbd9ee73981dd46aa0017fe157f9064c9b1daa7a" } } ], "extra": [ 1, 241, 254, 44, 229, 92, 248, 116, 218, 50, 204, 236, 77, 206, 174, 124, 38, 99, 46, 140, 112, 164, 154, 252, 45, 105, 50, 149, 163, 119, 241, 23, 215, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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