Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d79bde106afb3e1979f0f1b53394ee15c961f690ab028fa2c2b540e14d224297

Tx prefix hash: 7ece7c70b7584b1be77f394e3d32d50115abb95fb89d15437454ed84b9a7f3ac
Tx public key: 9f8c8ed537a8bdbe9a7d037481f5d7db8bdd3997a6998d519f0d509ccf095452
Timestamp: 1578826033 Timestamp [UCT]: 2020-01-12 10:47:13 Age [y:d:h:m:s]: 05:138:17:07:45
Block: 43884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1249337 RingCT/type: yes/0
Extra: 019f8c8ed537a8bdbe9a7d037481f5d7db8bdd3997a6998d519f0d509ccf0954520211000000094ac5aa02000000000000000000

1 output(s) for total of 439.139425382000 dcy

stealth address amount amount idx
00: 5266b9e911aec21d3cc5d6e7fdd9d7a8df46acbcc691b170df2748da9c6ee766 439.139425382000 79635 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": 43894, "vin": [ { "gen": { "height": 43884 } } ], "vout": [ { "amount": 439139425382, "target": { "key": "5266b9e911aec21d3cc5d6e7fdd9d7a8df46acbcc691b170df2748da9c6ee766" } } ], "extra": [ 1, 159, 140, 142, 213, 55, 168, 189, 190, 154, 125, 3, 116, 129, 245, 215, 219, 139, 221, 57, 151, 166, 153, 141, 81, 159, 13, 80, 156, 207, 9, 84, 82, 2, 17, 0, 0, 0, 9, 74, 197, 170, 2, 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