Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57441988be82b943d68d91595e4e9441af004e8e455e065cdc2a8c6ea7206471

Tx prefix hash: 010ddb40114dc4e69b06c8e61f9e77e604d136b7a4bcafb3f60c4064ea2978c8
Tx public key: e72e2b8de4cbf9a88c9b1b81d4f356b241f341976ff6b62dd0a3685f1e02ece6
Timestamp: 1735134678 Timestamp [UCT]: 2024-12-25 13:51:18 Age [y:d:h:m:s]: 00:356:15:49:21
Block: 1182914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252449 RingCT/type: yes/0
Extra: 01e72e2b8de4cbf9a88c9b1b81d4f356b241f341976ff6b62dd0a3685f1e02ece6021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 577c28a00cbbc0d16d55bf2fdf38735d7c176b7bbca8436a1ae4ad72955a06af 0.600000000000 1669353 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": 1182924, "vin": [ { "gen": { "height": 1182914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "577c28a00cbbc0d16d55bf2fdf38735d7c176b7bbca8436a1ae4ad72955a06af" } } ], "extra": [ 1, 231, 46, 43, 141, 228, 203, 249, 168, 140, 155, 27, 129, 212, 243, 86, 178, 65, 243, 65, 151, 111, 246, 182, 45, 208, 163, 104, 95, 30, 2, 236, 230, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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