Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a44a7097e957904fc8f5bf8a4a04a420befee20edd553befc88482d78495f34

Tx prefix hash: c0678d337f21dc94e1e1b5aefa726963fb3a52f8b4e7b3ad235ba369cd98c797
Tx public key: c33853dfe8a010246d197a119d8c387faf2d7163b3e7fc2d85710b264a2beee7
Timestamp: 1735531681 Timestamp [UCT]: 2024-12-30 04:08:01 Age [y:d:h:m:s]: 00:101:00:13:38
Block: 1186185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71991 RingCT/type: yes/0
Extra: 01c33853dfe8a010246d197a119d8c387faf2d7163b3e7fc2d85710b264a2beee7021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0f271fb9d7dd4222133e6067c9758a06dfc09026295d1adf8714de0acaa9553 0.600000000000 1672664 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": 1186195, "vin": [ { "gen": { "height": 1186185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0f271fb9d7dd4222133e6067c9758a06dfc09026295d1adf8714de0acaa9553" } } ], "extra": [ 1, 195, 56, 83, 223, 232, 160, 16, 36, 109, 25, 122, 17, 157, 140, 56, 127, 175, 45, 113, 99, 179, 231, 252, 45, 133, 113, 11, 38, 74, 43, 238, 231, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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