Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c008e22712b8c8b6276f35112ea474f22d66fb8ad69fd1d6a655490ffe2fda7

Tx prefix hash: f5de27f6460113e5868be61f8d8c6c051f6f1443e419e8b087c76c267be07fce
Tx public key: 1d3101d2a54c39b7c249144254691580179d0a991fab6b9a1cdf2148c159929e
Timestamp: 1734460576 Timestamp [UCT]: 2024-12-17 18:36:16 Age [y:d:h:m:s]: 00:133:14:38:20
Block: 1177352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95299 RingCT/type: yes/0
Extra: 011d3101d2a54c39b7c249144254691580179d0a991fab6b9a1cdf2148c159929e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50a43e0aa8d1f5fbb3f97c7d6040836005f61fce0d68b6623ee9b234d3463bd7 0.600000000000 1663723 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": 1177362, "vin": [ { "gen": { "height": 1177352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50a43e0aa8d1f5fbb3f97c7d6040836005f61fce0d68b6623ee9b234d3463bd7" } } ], "extra": [ 1, 29, 49, 1, 210, 165, 76, 57, 183, 194, 73, 20, 66, 84, 105, 21, 128, 23, 157, 10, 153, 31, 171, 107, 154, 28, 223, 33, 72, 193, 89, 146, 158, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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