Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98f2080b863d4796a55b1f81342fb53c23568c0edcdf334920008705f7256b12

Tx prefix hash: bcec1a684ec51ec5a58c46a2615fc72f7bc8d0430e70cf60b44464aec7419ebc
Tx public key: 8e72f2a1fa71b230b8a44b9157a161c68d37a9fc8012efc099ab556a92c912c1
Timestamp: 1720694133 Timestamp [UCT]: 2024-07-11 10:35:33 Age [y:d:h:m:s]: 00:339:02:29:20
Block: 1063318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242227 RingCT/type: yes/0
Extra: 018e72f2a1fa71b230b8a44b9157a161c68d37a9fc8012efc099ab556a92c912c102110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d4f357bc4c0ca1e5bb9e510b323d18ed27f6db46b113af1a0d831a1be309db2 0.600000000000 1533833 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": 1063328, "vin": [ { "gen": { "height": 1063318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d4f357bc4c0ca1e5bb9e510b323d18ed27f6db46b113af1a0d831a1be309db2" } } ], "extra": [ 1, 142, 114, 242, 161, 250, 113, 178, 48, 184, 164, 75, 145, 87, 161, 97, 198, 141, 55, 169, 252, 128, 18, 239, 192, 153, 171, 85, 106, 146, 201, 18, 193, 2, 17, 0, 0, 0, 17, 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