Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6631804522fd6030e9079945607f40e770d3a5ced7ffd783f5f5ee36a49cf8ca

Tx prefix hash: cfc98ac8327ce3b28b3cb32b6e8a5b46b3b969fb6d10f4ba5c00c96a28b48e49
Tx public key: 60f86bee05b6db1de5a81e7a4f23248a76e2205c970ee08a6c09e1219bb02c1d
Timestamp: 1733149738 Timestamp [UCT]: 2024-12-02 14:28:58 Age [y:d:h:m:s]: 00:121:13:04:33
Block: 1166468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86662 RingCT/type: yes/0
Extra: 0160f86bee05b6db1de5a81e7a4f23248a76e2205c970ee08a6c09e1219bb02c1d0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91058a2a6551cd53ffe2835e354727d378cd043dc88da203c310d3709ecc73c8 0.600000000000 1652155 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": 1166478, "vin": [ { "gen": { "height": 1166468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91058a2a6551cd53ffe2835e354727d378cd043dc88da203c310d3709ecc73c8" } } ], "extra": [ 1, 96, 248, 107, 238, 5, 182, 219, 29, 229, 168, 30, 122, 79, 35, 36, 138, 118, 226, 32, 92, 151, 14, 224, 138, 108, 9, 225, 33, 155, 176, 44, 29, 2, 17, 0, 0, 0, 5, 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