Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70a728ff1e38c13a68c20d5c2f421254e90db0c4fff3ae665dbc840367b18526

Tx prefix hash: ef8781dd13256a755b6b45d6b7069984dd60ba857e68ac65b9c9632f0f38f7e8
Tx public key: a25d88f0d6e83de3929bf3a863a9832aee43aefecc4402793e8e7d5afc26c326
Timestamp: 1728783768 Timestamp [UCT]: 2024-10-13 01:42:48 Age [y:d:h:m:s]: 00:162:21:05:48
Block: 1130377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116183 RingCT/type: yes/0
Extra: 01a25d88f0d6e83de3929bf3a863a9832aee43aefecc4402793e8e7d5afc26c32602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91e5342f6913552c9b23ac41ef375b8140e8705089de16d839cdbc5320ec1f06 0.600000000000 1613252 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": 1130387, "vin": [ { "gen": { "height": 1130377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91e5342f6913552c9b23ac41ef375b8140e8705089de16d839cdbc5320ec1f06" } } ], "extra": [ 1, 162, 93, 136, 240, 214, 232, 61, 227, 146, 155, 243, 168, 99, 169, 131, 42, 238, 67, 174, 254, 204, 68, 2, 121, 62, 142, 125, 90, 252, 38, 195, 38, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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