Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cdef0d3c8e464480aec71b0ce12ae3f3a618868a7ac6dc913b965dd990acea0

Tx prefix hash: 46001c10599385c99f15eb410462ae57c8a0c1f4d051f0a807f69be5e639c71e
Tx public key: 3d0edb0f94239ab21476f419bfbc4cb26a925522de2501f5bc118240d710eb64
Timestamp: 1732824917 Timestamp [UCT]: 2024-11-28 20:15:17 Age [y:d:h:m:s]: 00:116:03:51:37
Block: 1163779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82813 RingCT/type: yes/0
Extra: 013d0edb0f94239ab21476f419bfbc4cb26a925522de2501f5bc118240d710eb640211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bee6508527ffe904feffe986fd22a0bdecb46049a1d113b6a8c8b0ea03c05fc2 0.600000000000 1649448 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": 1163789, "vin": [ { "gen": { "height": 1163779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bee6508527ffe904feffe986fd22a0bdecb46049a1d113b6a8c8b0ea03c05fc2" } } ], "extra": [ 1, 61, 14, 219, 15, 148, 35, 154, 178, 20, 118, 244, 25, 191, 188, 76, 178, 106, 146, 85, 34, 222, 37, 1, 245, 188, 17, 130, 64, 215, 16, 235, 100, 2, 17, 0, 0, 0, 1, 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