Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeeb37e75479b93f126ff1bcaa07b7f4b539b466ba465889dd068c2e3ba19395

Tx prefix hash: fb5c9d01d35035c1854b7c6c93639db5f1aa4eb8c7f0f97c7c9aa89c7c453cae
Tx public key: 7fd4305668502442ad22cb8516d2331de95820b5838e6e1f50c391913f6101af
Timestamp: 1736191236 Timestamp [UCT]: 2025-01-06 19:20:36 Age [y:d:h:m:s]: 00:093:08:54:41
Block: 1191649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66525 RingCT/type: yes/0
Extra: 017fd4305668502442ad22cb8516d2331de95820b5838e6e1f50c391913f6101af0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44450c5f6e66405567b9e9a5adc7100ddcb756389b4cfef6f09a12afcd1b1c17 0.600000000000 1678190 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": 1191659, "vin": [ { "gen": { "height": 1191649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44450c5f6e66405567b9e9a5adc7100ddcb756389b4cfef6f09a12afcd1b1c17" } } ], "extra": [ 1, 127, 212, 48, 86, 104, 80, 36, 66, 173, 34, 203, 133, 22, 210, 51, 29, 233, 88, 32, 181, 131, 142, 110, 31, 80, 195, 145, 145, 63, 97, 1, 175, 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