Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90e7ab3c6dd7bee001c20a2e23886ff3cf27e5e854c5d178bcd064420585b395

Tx prefix hash: 96f8f14c8f62d622041e511ddcf9553ed02e32d4e723a78b7e4b562f30c01264
Tx public key: 0cdfb114549d86fea8cd79f59d263330c49a9dbe32173ce81943ea0fe5a282a8
Timestamp: 1580376641 Timestamp [UCT]: 2020-01-30 09:30:41 Age [y:d:h:m:s]: 04:301:15:14:07
Block: 55252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106513 RingCT/type: yes/0
Extra: 010cdfb114549d86fea8cd79f59d263330c49a9dbe32173ce81943ea0fe5a282a80211000000028a2ee0d9000000000000000000

1 output(s) for total of 402.650287099000 dcy

stealth address amount amount idx
00: bff7a50c55ed40d6fc018b69eb387348c0efd67a0d71d2725620dc82dc68f854 402.650287099000 102040 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": 55262, "vin": [ { "gen": { "height": 55252 } } ], "vout": [ { "amount": 402650287099, "target": { "key": "bff7a50c55ed40d6fc018b69eb387348c0efd67a0d71d2725620dc82dc68f854" } } ], "extra": [ 1, 12, 223, 177, 20, 84, 157, 134, 254, 168, 205, 121, 245, 157, 38, 51, 48, 196, 154, 157, 190, 50, 23, 60, 232, 25, 67, 234, 15, 229, 162, 130, 168, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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