Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83ec69a511474fd3939c65341227ffe3c33389d49b22a6242e66f89205363e25

Tx prefix hash: d42ad2f1c70c5c54a789b457f77c200bdb4530e6adf3f6a66f892e67d670845b
Tx public key: 78fdf82a38ca242f8155eafd590653713b489182f00d602db35db671cf2dc648
Timestamp: 1728688152 Timestamp [UCT]: 2024-10-11 23:09:12 Age [y:d:h:m:s]: 00:203:15:41:07
Block: 1129589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145345 RingCT/type: yes/0
Extra: 0178fdf82a38ca242f8155eafd590653713b489182f00d602db35db671cf2dc648021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c5a0ef326dd5a226d7e1fe16f780a5ea12911db01a5d4e57b5543a6e8f47f94 0.600000000000 1612416 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": 1129599, "vin": [ { "gen": { "height": 1129589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c5a0ef326dd5a226d7e1fe16f780a5ea12911db01a5d4e57b5543a6e8f47f94" } } ], "extra": [ 1, 120, 253, 248, 42, 56, 202, 36, 47, 129, 85, 234, 253, 89, 6, 83, 113, 59, 72, 145, 130, 240, 13, 96, 45, 179, 93, 182, 113, 207, 45, 198, 72, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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