Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b536e48291d56b3b3a2c4ce3747ff5b746a9cdea5f91fb7c8f2a99f9564b2e7

Tx prefix hash: a1819f7fa927321e90e45cf9990f8c7548297018082dbab71d05a1882e489288
Tx public key: 151ec4c963ba7189cc8f233922b4a3dd8f2bb4aace6578c6473f270180a47287
Timestamp: 1574694692 Timestamp [UCT]: 2019-11-25 15:11:32 Age [y:d:h:m:s]: 05:150:06:23:47
Block: 17225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1250034 RingCT/type: yes/0
Extra: 01151ec4c963ba7189cc8f233922b4a3dd8f2bb4aace6578c6473f270180a47287021100000001f95225a5000000000000000000

1 output(s) for total of 538.179691570000 dcy

stealth address amount amount idx
00: b08b7f6d535164cfbe136a99a6ebd45798f48e4c2515c687a0d8483fa5e525b4 538.179691570000 24793 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": 17235, "vin": [ { "gen": { "height": 17225 } } ], "vout": [ { "amount": 538179691570, "target": { "key": "b08b7f6d535164cfbe136a99a6ebd45798f48e4c2515c687a0d8483fa5e525b4" } } ], "extra": [ 1, 21, 30, 196, 201, 99, 186, 113, 137, 204, 143, 35, 57, 34, 180, 163, 221, 143, 43, 180, 170, 206, 101, 120, 198, 71, 63, 39, 1, 128, 164, 114, 135, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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