Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94ae07800474aa3244aa7f0a2c5a03939bf7254a9d00350364b24d82212eb464

Tx prefix hash: f78414bee055f79158aa00e77b54ff7a852f486a7e08da631f2322fbc7a44114
Tx public key: f2d08d177fe86309298be4a8f8dee454e833d05575d64ea4150c0c796fb766b1
Timestamp: 1718323041 Timestamp [UCT]: 2024-06-13 23:57:21 Age [y:d:h:m:s]: 00:224:11:30:18
Block: 1043664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160584 RingCT/type: yes/0
Extra: 01f2d08d177fe86309298be4a8f8dee454e833d05575d64ea4150c0c796fb766b102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9e1ca5da7e0a99c7996af7ed11de062e85d6538013750560bd9f4abb2d4d99c 0.600000000000 1512821 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": 1043674, "vin": [ { "gen": { "height": 1043664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9e1ca5da7e0a99c7996af7ed11de062e85d6538013750560bd9f4abb2d4d99c" } } ], "extra": [ 1, 242, 208, 141, 23, 127, 232, 99, 9, 41, 139, 228, 168, 248, 222, 228, 84, 232, 51, 208, 85, 117, 214, 78, 164, 21, 12, 12, 121, 111, 183, 102, 177, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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