Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49814bfcccd58e947fd28823fae5c6db283da856bc5908e4df6839e0b10c7d2d

Tx prefix hash: bda8fbf65bcb7da362d134cff8cf80ff821207c0743d35e69edff14825077a22
Tx public key: 7b58920b45d8afa0bdf31b15c601e88a2e455fe1721f905b47c696e95c1aca07
Timestamp: 1574390525 Timestamp [UCT]: 2019-11-22 02:42:05 Age [y:d:h:m:s]: 05:038:03:10:28
Block: 14130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1170677 RingCT/type: yes/0
Extra: 017b58920b45d8afa0bdf31b15c601e88a2e455fe1721f905b47c696e95c1aca0702110000000566a80d00000000000000000000

1 output(s) for total of 551.050920468000 dcy

stealth address amount amount idx
00: de2c85d5855d917a0c4cca391258fe97fc01b4c2c58648b3c84bb332469e3bd6 551.050920468000 17518 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": 14140, "vin": [ { "gen": { "height": 14130 } } ], "vout": [ { "amount": 551050920468, "target": { "key": "de2c85d5855d917a0c4cca391258fe97fc01b4c2c58648b3c84bb332469e3bd6" } } ], "extra": [ 1, 123, 88, 146, 11, 69, 216, 175, 160, 189, 243, 27, 21, 198, 1, 232, 138, 46, 69, 95, 225, 114, 31, 144, 91, 71, 198, 150, 233, 92, 26, 202, 7, 2, 17, 0, 0, 0, 5, 102, 168, 13, 0, 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