Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 668786c49deae2cb17dce4b8646bf9b285cb352a9e369bb78e42e3803c339519

Tx prefix hash: d5877928fb186f4a35de009ca24cf1c82fcd938d14bfe7fce86497cff46cbfa1
Tx public key: 170d9f13745a9c06782ab9e4cbf3ba1f58e917525c26d2b5839abc0ac0c74e36
Timestamp: 1705502702 Timestamp [UCT]: 2024-01-17 14:45:02 Age [y:d:h:m:s]: 01:297:16:46:55
Block: 937347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471589 RingCT/type: yes/0
Extra: 01170d9f13745a9c06782ab9e4cbf3ba1f58e917525c26d2b5839abc0ac0c74e360211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdea898a23c07e40d4acd271c5ca9347264e4c7148b603842b9f9020755b2377 0.600000000000 1395397 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": 937357, "vin": [ { "gen": { "height": 937347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdea898a23c07e40d4acd271c5ca9347264e4c7148b603842b9f9020755b2377" } } ], "extra": [ 1, 23, 13, 159, 19, 116, 90, 156, 6, 120, 42, 185, 228, 203, 243, 186, 31, 88, 233, 23, 82, 92, 38, 210, 181, 131, 154, 188, 10, 192, 199, 78, 54, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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