Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f3bc2bbafa9479cbcc633e21e10acc1e78203b111d40e9fec2bccee5a135fcd

Tx prefix hash: 835d84e0600dd97e86b63ff91aa6fd245bc946c16e75e7063e7873e0a3bd86be
Tx public key: c1cafbe5244e972ff9d1e7ec607fa8558cdfd9fd981c8f723de3b28e40f16645
Timestamp: 1634924269 Timestamp [UCT]: 2021-10-22 17:37:49 Age [y:d:h:m:s]: 03:188:08:04:30
Block: 358250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 912722 RingCT/type: yes/0
Extra: 01c1cafbe5244e972ff9d1e7ec607fa8558cdfd9fd981c8f723de3b28e40f1664502110000000176fedcbd000000000000000000

1 output(s) for total of 39.901062963000 dcy

stealth address amount amount idx
00: e1535d82cb30f6627b222db25822c2cead28e80f19df65478cc61f775f557769 39.901062963000 730069 of 0

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": 358260, "vin": [ { "gen": { "height": 358250 } } ], "vout": [ { "amount": 39901062963, "target": { "key": "e1535d82cb30f6627b222db25822c2cead28e80f19df65478cc61f775f557769" } } ], "extra": [ 1, 193, 202, 251, 229, 36, 78, 151, 47, 249, 209, 231, 236, 96, 127, 168, 85, 140, 223, 217, 253, 152, 28, 143, 114, 61, 227, 178, 142, 64, 241, 102, 69, 2, 17, 0, 0, 0, 1, 118, 254, 220, 189, 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