Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0ee8ea23df9d8805604f8719afdb1a45bf2ca199e4173a5d4f70f277a16c062

Tx prefix hash: f4dabed6ac7acb8c2ab6b5e9f2907e4ad2d99f00caea0457da251105667c9516
Tx public key: f18578d1106e304e695e6607c75eca1505d7b3c3903fba991d42917c28e555ea
Timestamp: 1736999794 Timestamp [UCT]: 2025-01-16 03:56:34 Age [y:d:h:m:s]: 00:308:23:17:20
Block: 1198347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218315 RingCT/type: yes/0
Extra: 01f18578d1106e304e695e6607c75eca1505d7b3c3903fba991d42917c28e555ea02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14925a0a4829809488314d4bcfa431d2f9844e0c7d067e8ace5dfbbd818c4cd9 0.600000000000 1684970 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": 1198357, "vin": [ { "gen": { "height": 1198347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14925a0a4829809488314d4bcfa431d2f9844e0c7d067e8ace5dfbbd818c4cd9" } } ], "extra": [ 1, 241, 133, 120, 209, 16, 110, 48, 78, 105, 94, 102, 7, 199, 94, 202, 21, 5, 215, 179, 195, 144, 63, 186, 153, 29, 66, 145, 124, 40, 229, 85, 234, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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