Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 862a53e3e6179f19fd13baa264bb38d3544df7d1ca3d31b940fa46bad9b5d97c

Tx prefix hash: 2df4950ee8556d2468855b46dbb82a5e7f09ec1972051275758f41734fa6b279
Tx public key: 82b6d7aafd0cc8bba00e8d715599fc65bedcb4cdd0ee5844ae0dbe7a0f993a4e
Timestamp: 1722495512 Timestamp [UCT]: 2024-08-01 06:58:32 Age [y:d:h:m:s]: 00:270:05:42:21
Block: 1078244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193060 RingCT/type: yes/0
Extra: 0182b6d7aafd0cc8bba00e8d715599fc65bedcb4cdd0ee5844ae0dbe7a0f993a4e02110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e53534d270cb8fee333e47eb44c387fad397d2492e547dadaf716ba8abe04ca 0.600000000000 1550817 of 15

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": 1078254, "vin": [ { "gen": { "height": 1078244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e53534d270cb8fee333e47eb44c387fad397d2492e547dadaf716ba8abe04ca" } } ], "extra": [ 1, 130, 182, 215, 170, 253, 12, 200, 187, 160, 14, 141, 113, 85, 153, 252, 101, 190, 220, 180, 205, 208, 238, 88, 68, 174, 13, 190, 122, 15, 153, 58, 78, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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