Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344343fd9124e9a8c1ea43e8b1e5992684a4d7ff17a496bbd331363ff554ada9

Tx prefix hash: c35adde6dc76488dcdeccae250c8701ca238698fba37d59b712f4ea0bdc7b8c0
Tx public key: cfe527a320b4b463a9cb1c30067645dfb55293ecbb5f9431e06cf5ba8d6fac95
Timestamp: 1710678700 Timestamp [UCT]: 2024-03-17 12:31:40 Age [y:d:h:m:s]: 01:087:02:02:53
Block: 980295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323214 RingCT/type: yes/0
Extra: 01cfe527a320b4b463a9cb1c30067645dfb55293ecbb5f9431e06cf5ba8d6fac950211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bba97535148395bd028daba750d66927c5f0a0ee107b19e8d7e3669a22bd0c68 0.600000000000 1440360 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": 980305, "vin": [ { "gen": { "height": 980295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bba97535148395bd028daba750d66927c5f0a0ee107b19e8d7e3669a22bd0c68" } } ], "extra": [ 1, 207, 229, 39, 163, 32, 180, 180, 99, 169, 203, 28, 48, 6, 118, 69, 223, 181, 82, 147, 236, 187, 95, 148, 49, 224, 108, 245, 186, 141, 111, 172, 149, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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