Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04ef2fd5811b5ab69e7fc8ca741a4175007d34c401551e56d88843545638a22b

Tx prefix hash: 2c687aef6e53e3f03bd2a051bf7a9eaf7ffa48fa1c7ec4a91d8106f90726878a
Tx public key: c021976e1d0692a8ddfc4fa94df712d5548d3f1f605204a62d478c01ce124003
Timestamp: 1583518060 Timestamp [UCT]: 2020-03-06 18:07:40 Age [y:d:h:m:s]: 05:216:09:51:18
Block: 77414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1307770 RingCT/type: yes/0
Extra: 01c021976e1d0692a8ddfc4fa94df712d5548d3f1f605204a62d478c01ce1240030211000000094943cd9f000000000000000000

1 output(s) for total of 340.013433382000 dcy

stealth address amount amount idx
00: 44a8f69f5d15d19bea5d49d938453d93626520ab3e91c3e287ea06f6471c0570 340.013433382000 142521 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": 77424, "vin": [ { "gen": { "height": 77414 } } ], "vout": [ { "amount": 340013433382, "target": { "key": "44a8f69f5d15d19bea5d49d938453d93626520ab3e91c3e287ea06f6471c0570" } } ], "extra": [ 1, 192, 33, 151, 110, 29, 6, 146, 168, 221, 252, 79, 169, 77, 247, 18, 213, 84, 141, 63, 31, 96, 82, 4, 166, 45, 71, 140, 1, 206, 18, 64, 3, 2, 17, 0, 0, 0, 9, 73, 67, 205, 159, 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