Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d8860eb6cd1a725d7956bf06662608c541214fe662994b781d0e4aa85ccff4

Tx prefix hash: 4cc43e4d63aa1ba6030248ea5aa4b61c3dbbe3e143253bed203f1f86f163a941
Tx public key: 70e9e976bc6f7516af18f41ebc89930b3ab7c686771aba2d135f2b1ad4170671
Timestamp: 1577907316 Timestamp [UCT]: 2020-01-01 19:35:16 Age [y:d:h:m:s]: 04:334:07:10:03
Block: 36563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128131 RingCT/type: yes/0
Extra: 0170e9e976bc6f7516af18f41ebc89930b3ab7c686771aba2d135f2b1ad4170671021100000036c3a1a09f000000000000000000

1 output(s) for total of 464.357490659000 dcy

stealth address amount amount idx
00: f2041669f1873ec4f56b0e81a04d85b68e86f1e22d8e4a87e6bab3e2bfaf53c4 464.357490659000 61960 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": 36573, "vin": [ { "gen": { "height": 36563 } } ], "vout": [ { "amount": 464357490659, "target": { "key": "f2041669f1873ec4f56b0e81a04d85b68e86f1e22d8e4a87e6bab3e2bfaf53c4" } } ], "extra": [ 1, 112, 233, 233, 118, 188, 111, 117, 22, 175, 24, 244, 30, 188, 137, 147, 11, 58, 183, 198, 134, 119, 26, 186, 45, 19, 95, 43, 26, 212, 23, 6, 113, 2, 17, 0, 0, 0, 54, 195, 161, 160, 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